docs(skill): a carry orphans its source, and splitting a rate needs a correction - #363

… correction

Four sections. A carry re-cut onto a fresh base has a new tree and a new
patch-id, so no content route connects it back and the bee's original branch
becomes permanent debt - read the commit message instead, which L1 makes
load-bearing. The landing rule had a second copy in close-done that never
learned any of it. A conflict says two sides touched the same lines and says
nothing about which side is behind: rebasing browseros-ai#1302 would have deleted landed
work and reintroduced an L3 violation, so measure how far the base has moved
instead. And splitting a rate by category is several tests at once - four groups
at 95% each carry a 19% chance of a false alarm, which is how a dashboard earns
the right to be ignored.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>